Thank you, always. For the excellent work you do.

Hi Kirgman.

I recently encountered a problem that I can't find a solution for.

It's an unwanted effect when I use the alpha channel and two surfaces are very close together.

It doesn't create an unwanted shadow. Rather, it creates a bounce of indirect light, creating shadow or light depending on the indirect light value.

I have to adjust the value to make the effect disappear, compromising the lighting I really want.

I've used the Centileo tag on the affected objects, which allows me to avoid them being affected by the GI, but the desired effect isn't achieved.

Best.

Thank you so much, Kirgman.

You have been very quick. I have tested it on the RTX 5090 and it works perfectly, except for the normal map values on some objects. But that's a minor bug.

I'll just have to modify some values.

Great work. Now the render engine is blazing fast.

Hi again Kirgman.

Could it be that you have adopted OSL for the Centileo materials? That would make sense of the increased values in the normal map and reflection among other things.

That problem has occurred in render engines like Redshift. That by adopting Osl, the values in many sections have gone from 1 to 100.

Sorry for the disctraction.

Scene sent.

mail sent.

Hi Kirgman.

I have not been able to do an in depth review, but these are some of the points I have observed.

Apologies if I'm being so candid. Testing with version 0.700 has been a bit disappointing. I understand that it is a first version, but there are things that involve profound changes in the render engine, such as having removed the “Projection” tab within the Centileo/Camera render settings.

In my particular case it has profound implications since I have been developing a tool in expresso for 2 years that is very integrated with centileo and some functions no longer make the correct call, because the component does not exist. Likewise, I have noticed that the structure of the materials has also changed with the same result for me.

As positive points I have observed a devilish speed when generating textures, the quality of the alphas has improved a lot and also the speed in general (keep in mind that it is running on a RX 5090 and this biases the conlusions at the level of speed).

Another thing I liked is that the texture mapping is stored directly in RAM.

In a little deeper examination testing both versions centile 0.698 and 0.700 and on both RTX 4090 and 5090 platforms. I have drawn some conclusions that are complex to explain over here.

So I will send a mail from which you can download a PUREREF that will give you a clearer view.

Regards and thanks.

Thanks for your quick response.

Hi Kirgman.
I just upgraded to rtx 5090 and centileo does not render in IPR (Render directly I have not tried)
Is Centileo currently compatible with RTX 5090?

The truth is that centileo has been growing in recent times and it would be fantastic to be able to have it.

In any case, congratulations for the powerful render engine you are creating.

And thanks for the titanic effort and time you dedicate to listen to people in the forum.

A sample of the integration of gaussian spplating in c4d and redshift.
https://www.reddit.com/r/RedshiftRenderer/comments/1jpleko/check_this_out_we_pu­blished_our_first_plu...

It would be very useful for recreating scenery and exteriors. In my case, I am dedicated to the recreation of soccer stadiums and formula 1 circuits. It would be very useful.

Capturing the location to place my models in the middle.

Not being able to see them up close would greatly reduce production time.

Hi Kirgman.

Are you contemplating the possibility of incorporating Gaussian splatting in future versions of Centileo?

Quote

Kirgman wrote: jiv21 , hi! I have fixed the slowdown, now the new version is even slightly faster on your scene. The issue was in the fact that you configured the stadium scenes with many collections of Mograph multi-instances. In 0.68 they were built as a single union collection. In earlier 0.69 they were built separately because of new shader flexibility. Now the flexibility and performance considerations are combined efficiently. Thanks to your bugreport the renderer has become even better! Thank you very much! Btw, this is Juventus stadium. But I want to say Forza Inter! I am fan of Inter for 26 years already.

What good news.

Thanks for the explanation. I'm not a programmer, but I remember commenting that maybe that was the problem.

I work with several 3d software packages and render engines and in the end one encounters many issues that tends to narrow down where the problem could be

You are right. It is the juventus stadium “Allianz Stadium”.

I hope that sooner rather than later juventus will come back to delight us with the successes of the past.

Thanks again.

Mail sent. Good luck with the scene and I hope it doesn't take too much of your time to find the problem.

On another hand, I would appreciate it if you do not share or make the scene public.

Apologies for the wrong file name.

Hi Kirgman.

I have already adapted the scene by removing my tool and eliminating everything that can reduce the size of the scene but it doesn't eliminate the problem.

I have removed all unused materials, alembics, Xpresso, user data, etc.

Still the loss of performance is still occurring. The time is 1.25 in Centile 0.680 and 2.26 in Centile 0.697.

Although the images show a different time (1.45/2.48) the difference is still 1 minute.

As soon as you provide me with a contact email I will send you a link to download the scene.

I am using cinema4D 2024.5. If you use version 2025.0.1 you will get an error because one of the components of version 2024.5 is no longer in 2025.0.1. You must delete it or else it will not let you save any changes you make in the scene.

Hi kirgman.

The scenes are very large because they use recurring resources such as seats, trees and HD animated characters, and the project can reach 60GB.

On the other hand, it has an integrated tool for the creation of stadiums that I have been developing for a year and a half. So in order to send it to you, I would have to remove the whole part of the tool. Then I would remove all the characters to check if the loss of performance is still occurring and thus do not create a project so large to send it.

I beg your patience because right now I am closing a project and the number of hours I dedicate daily does not leave me time for anything else.

What I can tell you is that I make an intensive use of cloners in all its modalities. Instance, render instance and multi instance. In case you have any idea.

I usually use normal maps. I do not usually use relief maps and on rare occasions displacement maps.

As soon as I have some time available I will send you a scene.

Thank you for the clarifications.

Attached is the Centileo configuration.

Thanks again Kirgman.

I am quite busy at the moment finalizing a project. But as soon as I have a moment, I'll check a scene for you to study it.

Comment that the performance problem has been reproduced in each and every one of the scenes I have created. So that is the reason for my first question in the forum. If I had detected that it only affected one scene, I would have thought about it before publishing in the forum (sowing the doubt).

I respect your work very much.